SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 52753: The UPCASE function used in PROC SQL UPDATE might not work properly if you are using SAS/ACCESS® Interface to OLE DB

DetailsHotfixAboutRate It

When you use a PROC SQL UPDATE statement on a database management table accessed via the OLEDB LIBNAME engine, rows that should be updated might not be updated. This issue might occur when your WHERE clause includes a function that does not get passed to the database. The UPCASE function is a good example.

libname test oledb init_string="Provider=SQLOLEDB.1;Password=db-password;User ID=db-user;Data Source=xxx";
proc sql;
update test.class
set age=15
where update(name)='ALFRED';
quit;

Instead of the database processing the WHERE clause, SAS does the processing. The data read in from the database is not transcoded correctly, resulting in matches not being found. As a result, the data is not updated as it should be. 

A potential workaround for this issue is to use the LIBNAME option SQL_FUNCTIONS=ALL. This workaround results in additional SAS functions being passed down to the database.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS/ACCESS Interface to OLE DBMicrosoft® Windows® for x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Enterprise 32-bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Enterprise x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Pro 32-bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Pro x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Enterprise 32-bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Enterprise x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Pro9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Pro 32-bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2003 Datacenter Edition9.3_M29.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition9.3_M29.3 TS1M2
Microsoft Windows Server 2003 Standard Edition9.3_M29.3 TS1M2
Microsoft Windows Server 2003 for x649.3_M29.3 TS1M2
Microsoft Windows Server 20089.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2008 R29.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2008 for x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 Datacenter9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 R2 Datacenter9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 R2 Std9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 Std9.3_M29.4_M29.3 TS1M29.4 TS1M2
Microsoft Windows XP Professional9.3_M29.3 TS1M2
Windows 7 Enterprise 32 bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows 7 Enterprise x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows 7 Home Premium 32 bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows 7 Home Premium x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows 7 Professional 32 bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows 7 Professional x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows 7 Ultimate 32 bit9.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows 7 Ultimate x649.3_M29.4_M29.3 TS1M29.4 TS1M2
Windows Vista9.3_M29.3 TS1M2
Windows Vista for x649.3_M29.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.